Short message service protocol gateway

ABSTRACT

A system for communicating short message service messages from a SMS application to a wireless communication device. The system includes a protocol gateway for converting messages from a simple object access protocol (SOAP) to a short message peer-to-peer (SMPP) protocol. By using a SOAP protocol for a portion of communications between the SMS application and the wireless communication device, the system provides communications path in which SMS application is not required to maintain knowledge of the complex SMPP protocol. The system may also include a billing mechanism for charging subscribers for content received by the wireless communication device.

CROSS REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. application Ser. No.11/467,335, filed Aug. 25, 2006 now U.S. Pat. No. 8,068,960, theentirety of which is herein incorporated by reference.

FIELD OF THE INVENTION

The present invention generally relates to the field oftelecommunications. More particularly, the invention relates toproviding messaging services within a wireless network.

BACKGROUND

Mobile telephone messaging networks commonly provide short textmessaging capabilities such as, for example, a standard Short MessageService (SMS) that supports transmission of alphanumeric messagesbetween mobile telephone subscribers and other short message devices.Current standards provide for message lengths up to 140 bytes for singlemessages. For example, a short message (e.g., “Please remember to pickup the dry cleaning”) may be sent from a first wireless phone to asecond wireless phone and may appear on a display of the second wirelessphone.

A number of protocols exist that can be used to transmit SMS messages.One such protocol is the Short Message Peer to Peer (SMPP) messagingprotocol. This protocol was published as “Short Message Peer to PeerProtocol Specification” (version 3.4, Issue 1.2, Oct. 12, 1999)(available at http://www.smpp.org/). SMS messages may be routed betweena mobile telephone messaging network and different SMS data applicationsvia an SMPP gateway.

Current SMPP interfaces for SMS applications are robust; however, theSMPP protocol is not well known and requires specific knowledge of theunderlying wireless network and its technology for successfulimplementation.

Therefore, there is a need for a system and method for providing asimplified interface for sending and receiving SMS messages by wirelesssubscribers using a SMS application.

SUMMARY OF THE INVENTION

The present invention, in one embodiment, includes a method of sending amessage between a short message service application and a wirelesscommunication device. The method can include sending an SMS servicerequest from an SMS application to a gateway in one protocol, convertingthe SMS request in that protocol into another protocol, and sending theSMS request to a second gateway. From there the short message servicerequest having the second protocol can be routed to a message center fordelivery to the wireless communication device.

In some embodiments the first protocol can be a SOAP protocol, and thesecond protocol can be an SMPP protocol. A billing server can be used inthe method to generate a billing record and bill a subscriber for SMSmessages and content received by the subscriber. A bulk short messageservice request can be sent in some embodiments where the bulk shortmessage service request includes common message content and a list ofdestination addresses. In some embodiments, the first gateway cangenerate separate send requests in the second protocol for eachdestination address in the bulk short message service request, with eachseparate send request including the common message content.

The invention further includes a system for sending a message between anSMS application and a communication device that comprises a shortmessage service application, a protocol gateway, an SMPP gateway and amessage center. The protocol gateway can convert a message from a firstprotocol to a second protocol. The SMPP gateway can receive the messagein the second protocol from the protocol gateway. The message center canreceive the message in the second protocol from the SMPP gateway anddeliver it message to a communication device. The first protocol can bea SOAP protocol and the second protocol can be an SMPP protocol. Thesystem can include a billing server configured to generate a billingrecord for billing a subscriber for SMS messages and content received bythe subscriber.

In yet another embodiment, the invention comprises a protocol gatewayfor use in sending short messaging service messages. The protocolgateway can receive a message in a first protocol from a short messageservice application, convert the message to a second protocol, and sendthe message in the second protocol to a second gateway. The firstprotocol can be a SOAP protocol and the second protocol can be an SMPPprotocol. The protocol gateway can send a purchase request to a billingserver to charge for message content, and can process bulk short messageservice requests that include common message content and a list ofdestination addresses. The protocol gateway can generate separate sendrequests in the second protocol for each destination address. Theprotocol gateway can receive delivery responses for separate sendrequests, assemble the responses to generate a composite response, andforward the composite response to a short message service application.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram illustrating a protocol gateway networkarchitecture according to a first embodiment of the present invention.

FIG. 2 is a diagram illustrating a method for sending a mobileterminated message using the first embodiment of the present invention.

FIG. 3 is a diagram illustrating a method for receiving a mobileoriginated message by a SMS application.

FIG. 4 is a diagram illustrating a method for sending a delivery reportfrom a message center to an originating application via a protocolgateway.

FIG. 5 is a diagram illustrating a method for sending a bulk message viathe invented protocol gateway.

FIG. 6 is a diagram illustrating a method for verifying destinationaddresses within a network architecture utilizing a protocol gateway.

FIG. 7 is a block diagram illustrating a protocol gateway networkarchitecture according to a second embodiment of the present invention.

FIG. 8 is a diagram illustrating a method for providing a mobileterminated message within the second embodiment.

FIG. 9 is a diagram illustrating a method for a sending bulk messagefrom the within the second embodiment.

DETAILED DESCRIPTION OF THE INVENTION

As required, detailed embodiments of the present invention are disclosedherein. It must be understood that the disclosed embodiments are merelyexemplary of the invention that may be embodied in various andalternative forms, and combinations thereof. As used herein, the word“exemplary” is used expansively to refer to embodiments that serve as anillustration, specimen, model or pattern. The figures are notnecessarily to scale and some features may be exaggerated or minimizedto show details of particular components. In other instances, well-knowncomponents, systems, materials or methods have not been described indetail in order to avoid obscuring the present invention. Therefore,specific structural and functional details disclosed herein are not tobe interpreted as limiting, but merely as a basis for the claims and asa representative basis for teaching one skilled in the art to variouslyemploy the present invention.

FIG. 1 is a protocol gateway network architecture 100 in accordance withthe first embodiment of the present invention. The protocol gatewaynetwork architecture 100 includes a protocol gateway 102, which can beused for conversion of messages that are in a, for example, simpleobject access protocol (SOAP) format to messages that are in shortmessage peer-to-peer protocol (SMPP) format. Also included is a SMPPgateway 104, and an SMS content provider 108. The SMPP Gateway isconnected to a number of message centers, 213, 215, and 217. The SMScontent provider 108 can use SMS to send content directly to the devicesuch as ringtones, news and stock alerts as is known in the art. The SMScontent provider 108 can also send SMS messages that alert a device toperform an operation (for example, to download a ringtone, video, ore-mail). The SMS content provider may have one or more SMS applications201. Although shown in FIG. 1 as located between the internet 132 andthe protocol gateway 102 of the wireless network, the SMS contentprovider 108 and SMS application 201 can be located on the internet 132with the protocol gateway being connected to the SMS content provider108 through the internet 132. The configuration shown in FIG. 1,however, can provide additional security advantages over the alternateconfiguration.

The protocol gateway network architecture 100 may also include theInternet 132, an email client 130, and a directory server 211 which caninclude subscriber data and routing rules.

FIG. 2 is a diagram 200 illustrating the transfer of a mobile terminatedmessage from an SMS application 201 to the protocol gateway 102. At 202and 204, the SMS application 201 and the protocol gateway 102 performauthorization and encryption handshaking in order to determine that theSMS application 201 is authorized to access the protocol gateway 102 andto prevent message data from being intercepted.

At 206, the SMS application 201 submits an SMS request, shown on thediagram as “Submit_SMS.REQ”, to the protocol gateway 102. This requestcontains message information intended for a mobile station as well asinformation identifying the intended recipient, such as a mobiledestination number (e.g., a telephone number associated with a mobiledevice). The request can also contain the an address of the SMSapplication, such as an IP address or a domain name which resolves tothe IP address. Data elements of such a request are later described indetail, but can contain the message to be sent and informationidentifying the intended recipient or identifying a device for which themessage is intended. The request can be submitted in a SOAP format. Theprotocol gateway 102 receives the SOAP formatted SMS request andperforms a conversion operation on the SOAP formatted message. Thisconversion maps the message information from the relatively simple ASCIIXML-based SOAP format to the more complicated binary SMPP protocol.

At 208, the protocol gateway 102 forwards the request (now in an SMPPformat) to the SMPP gateway 104. At 210, the SMPP gateway 104 queries adirectory server 211 for routing information regarding where the SMPPgateway should forward the SMPP message based on the intended recipientof the message. The query can contain information regarding the intendedrecipient of the message. For example, the mobile number of a wirelessdevice associated with the intended recipient can be included in thequery. At 212, the directory server 211 returns a response to the SMPPgateway 104 based on the supplied information regarding the intendedrecipient of the message that indicates to which message center themessage should be sent to provide for proper delivery of the message.Next at step 214, the SMPP gateway 104 forwards the message request tothe message center 215 indicated in the response from the directoryserver.

Once the message has been received by the message center 215, themessage center 215 submits a response message 216 to the SMPP gateway104. The response message submission is labeled “Submit_SM_Resp( )” onthe diagram. The response includes information identifying the SMSapplication 201 for which it is intended. This identifying informationcan be, for example, an IP address and port number of a server on whichthe SMS application is installed. It should be understood that this isnot a verification that the message has been delivered to the intendedrecipient. SMS message centers operate as store and forward nodes. Thatis, messages sent to the message center 215 are stored in the messagecenter 215 for later forwarding to the intended recipient. There is noguarantee that the intended recipient will receive the message. An SMSmessage center uses a “best effort” mode of operation. If the intendedrecipient is a mobile customer that, for example, does not register withthe wireless network for a number of days, the message may never bedelivered, and instead discarded.

The response 216 is received at the SMPP gateway 104. The SMPP gatewayforwards the response to the protocol gateway at 218. A routing rule canexist at the SMPP gateway to specify that for responses intended for theaddress of the SMS application, the response should be routed to theprotocol gateway 102. The protocol gateway 102 performs a conversionoperation on the SMPP formatted response to create a SOAP formattedresponse. At 222, the SOAP formatted response is sent to the SMSapplication 201.

The protocol gateway 102 can reject the mobile terminated messagebecause of invalid content, protocols, or authorization errors. The SMPPgateway 104 can reject the mobile terminated message because the SMPPgateway 104 receives an invalid destination address (for example, aninvalid mobile telephone number), or the destination address is not thewithin wireless network (such information can be obtained from thedirectory server or a number resolution service to be discussed infra.)Also, the message center may reject a SMS message due to a permanentdelivery failure.

FIG. 3 is a diagram 300 illustrating the transfer of a mobile originatedmessage from a mobile station (not shown) to an SMS application 201. Themessage is sent from the mobile station, such as a wireless telephone,to its corresponding message center 215. The message can containdestination information for the message and be in an SMPP protocolformat. At 302, the message center 215 sends a delivery request to theSMPP gateway 104 containing the message sent from the mobile device. At304, the SMPP gateway 104 sends a routing data request to the directoryserver 211 to determine where the message should be routed based on thedestination information. At 306, the directory server 211 issues aresponse to the SMPP gateway 104.

At 308, the SMPP gateway 104 sends a delivery request to the protocolgateway 102. The message can be in an SMPP format. The protocol gateway102 can perform a conversion operation on the message, mapping the datacontained in the SMPP format to data fields of a SOAP format. Theprotocol gateway 102 forwards the SOAP formatted message to the SMSapplication 201 at 310.

At 312, the SMS application 201 issues a delivery response to theprotocol gateway 102. This response is labeled as “Deliver_SMS.RES” onthe diagram. The protocol gateway 102 performs conversion operations onthe SOAP formatted delivery response to create an SMPP formattedresponse. At 314, the SMPP formatted response is sent to the SMPPgateway 104. At 316, the SMPP formatted response is forwarded to themessage center 215 that originated the message at 302.

FIG. 4 is a diagram 400 illustrating a process where a delivery reportis requested for a submitted message request. The process is similar tothat depicted in FIG. 2 for sending the message to the intendedrecipient and providing the response from the message center 215 thatthe message was received for delivery. In the case of FIG. 4, however,the submitted request (“Submit_SMS.REQ”) includes a deliverynotification flag (which is set to “1” or “yes”) which is an indicationthat the SMS application 201 requests a delivery notification for thesubmitted message. As noted above, SMS message centers operate as storeand forward nodes. After receiving the message, the message center willattempt to deliver the message to the intended recipient. If, as in thecase shown in FIG. 4, the delivery notification flag is set, the messagecenter 215 will initiate a delivery response to the SMS application uponsuccessful delivery of the message to its intended recipient. Thedelivery response can be sent in all cases, whether the delivery attemptwas successful or not. The delivery report can contain the final stateof the message, delivered successfully, permanent error, message expiredundelivered (for example, the mobile device could not be reached withina specific time, from hours to days).

Operation up to 402 is similar to that described above regarding FIG. 2with the exception of a delivery notification flag being set in theinitial request. At 402, the message center 215 sends an SMPP formatteddelivery notification to the SMPP Gateway 104. At 404, the SMPP Gatewayrequests routing information from the directory server 211. At 406, thedirectory server returns information to the SMPP Gateway indicating thelocation of the protocol gateway 102. At 408, the SMPP Gateway uses theinformation provided by the directory server 211 to forward the deliverynotification to the protocol gateway 102. The protocol gateway 102receives the SMPP formatted delivery notification, and performs aconversion operation on the delivery notification to create a SOAPformatted delivery notification that is sent at 410 to the SMSapplication 201.

At 412, the SMS application 201 issues a delivery report response to theprotocol gateway 102. The protocol gateway 102 receives the SOAPformatted delivery report response and performs a conversion operationon the SOAP formatted response to create an SMPP formatted response. TheSMPP formatted response is forwarded to the SMPP Gateway 104 at 414. At416, the delivery response is forwarded to the message center.

It should be understood that the delivery report 402 sent from themessage center can be initiated by other events other than successfuldelivery of the message. For example, events such as a permanent erroror message expiration at the message center can also trigger thetransmission of the delivery report.

FIG. 5 is a diagram 500 illustrating a bulk send of a message by the SMSapplication 201 using the protocol gateway 102. At 502, a bulk sendrequest which can be in a SOAP format is sent by the SMS application 201to the protocol gateway 102. The bulk send request is labeled as“Submit_Bulk_SMS.REQ” in the diagram. The bulk send request containsmessage content that will be common to all recipients and a list ofdestination addresses to which to send the message content. Thedestination addresses can comprise a list of mobile telephone numbers towhich the message is intended. The destination addresses can alsocomprise email addresses, or a combination of mobile telephone numbersand email addresses. At 504, a SOAP formatted bulk send response is sentback to the SMS application by the protocol gateway 102. The protocolgateway 102 performs a conversion operation on the SOAP formatted bulksend request to create an SMPP formatted send request. A separate sendrequest is created for each destination address contained in the SOAPbulk send request received from the SMS Application 201. At 506, theprotocol gateway 102 submits an SMPP formatted send request to the SMPPgateway 104 for one of the intended recipients. At 508, the SMPP gateway104 sends a routing data request to the directory server 211. At 510,the directory server returns a routing data response to the SMPP gateway104 indicating which message center the SMPP Gateway should send therequest to for delivery. At 512, the SMPP gateway 104 submits the sendrequest to the message center 215 for delivery.

At 514, the message center 215 issues a response confirming that themessage has been received at the message center 215. Again, this is nota confirmation that the message has been delivered; only that it hasbeen received at the message center 215. The confirmation response issent from the message center 215 to the SMPP Gateway 104. The SMPPGateway forwards this response to the protocol gateway 102 at 516. Theprotocol gateway 102 records that one of the bulk messages was receivedat the message center. The destination address of the original messagecan be used to identify to which of the messages from those submitted inthe list that the confirmation message corresponds.

The actions 506, 508, 510, 512, 514, and 516, enclosed in dotted line519 are repeated for each destination address in the bulk send request.

At 520, the protocol gateway 102 sends a SOAP formatted message to theSMS application 201 to confirm that the plurality of messagescorresponding to the initial bulk status request were received by theirrespective message centers. This message can also indicate if there werefailures of delivery to the message center(s) for one or more intendedrecipients and which recipients those were. At 522, the SMS application201 sends a response to the protocol gateway 102 to indicate that theconfirmation was received.

Thus, the protocol gateway 102 allows the SMS application 201 to submita single message and a list of destination addresses for delivery toeach address. The protocol gateway 102 collects responses for eachmessage from their respective message centers (whether successful orunsuccessful) and assembles them into a response, which can be forwardedto the SMS application.

FIG. 6 is a diagram 600 illustrating a process for determiningdestination address validity using the protocol gateway 102. At 602, theSMS application 201 sends a validity request to the protocol gateway102. The request can contain multiple destination addresses. At 604, theprotocol gateway 102 returns a response to the validity request to theSMS application to acknowledge receipt of the request. The protocolgateway 102 performs conversion operations on the SOAP formattedvalidity request to create one or more validity requests. At 606, theprotocol gateway 102 sends a query to a number resolution service 601.The number resolution service can comprise a number resolution server.At 608, the number resolution service 601 submits a response to thequery back to the protocol gateway 102. The query at 606 and theresponse at 608 can use lightweight directory access protocol (LDAP).The actions at 606 and 608 contained in dotted line 609 are repeated foreach of the destination addresses contained in the initial request fromthe SMS Application 201.

The protocol gateway 102 assembles the response messages from the numberresolution service 601 to create a SOAP formatted composite responsemessage. At 610, the protocol gateway sends the composite responsemessage to the SMS application 201. At step 612, the SMS application 201submits a response back to the protocol gateway 102 acknowledging thatthe response was received.

With the ability to check the validity of a destination address, theprotocol gateway network architecture 100 provides a capability whichallows the SMS application 201 to determine if a directory number is avalid number within a wireless network before the SMS application 201sends messages to a communication device. The protocol gateway networkarchitecture 100 also allows the protocol gateway 102 to query a numberresolution service to determine if a directory number is assigned to agiven wireless service.

FIG. 7 is a protocol gateway network architecture 700 in accordance withthe second embodiment of the present invention. The protocol gatewaynetwork architecture 700 is similar to the protocol gateway networkarchitecture 100 and additionally includes a billing server 702. Theprotocol gateway 102 can be connected to the billing server 702. Byhaving an interface with the billing server 702, the protocol gatewaynetwork architecture 700 has the ability to charge for message contentassociated with a particular subscriber.

FIG. 8 is a diagram 800 illustrating the transfer of a mobile terminatedmessage by an SMS application 201, which includes actions for creating abilling record. At 802, the SMS application 201 sends a message requestto the protocol gateway 102. This message can be in a SOAP format. At804, the protocol gateway 102 sends a purchase request to the billingserver 702. This request can contain information identifying the mobileterminal and/or associated wireless account for which a message isintended. This identification can be, for example, a mobile telephonenumber. The billing server 702 records the information identifying themobile terminal in a billing record. This billing record can also recordadditional information passed on to the billing server 702 from theprotocol gateway 102 such as the amount of data contained in themessage. Other information provided can include but is not limited tothe type of the content of the message, and the price of the content.The amount charged to a wireless account can be based on the amount ofdata contained in the message. At 806, the billing server 702 issues aresponse to the purchase request to the protocol gateway 102 confirmingreceipt of the purchase request and creation of the billing record.

The protocol gateway 102 can perform a conversion operation on the SOAPformatted message submitted from the SMS Application 201. The conversionoperation can create a SMPP formatted message. At 808, the protocolgateway 102 submits the SMPP formatted message to SMPP gateway 104. At810, the SMPP gateway 104 queries a directory server 211 for routinginformation regarding where the SMPP gateway should forward the SMPPmessage based on the intended recipient of the message. At 812, thedirectory server 211 returns a response to the SMPP gateway 104 thatindicates which message center the message should be sent in order forproper delivery of the message to the intended mobile station recipient.At 814, the SMPP gateway 104 forwards the message request to the messagecenter 215 indicated in the response from the directory server 211.

Once the message has been received by the message center 215, themessage center 215 submits a response message 816 to the SMPP Gateway104. The response message submission is labeled “Submit_SM_Resp( )” onthe diagram. The response includes information identifying the SMSapplication 201 for which it is intended. This identifying informationcan be, for example, an IP address and port number of a server on whichthe SMS application 201 is installed. It should be understood that thisis not a verification that the message has been delivered to theintended recipient. Message centers operate as store and forward nodes.That is, messages sent to the message center are stored in the messagecenter for later forwarding to the intended recipient. There is noguarantee that the intended recipient will receive the message. Amessage center uses a “best effort” mode of operation. If the intendedrecipient is a mobile customer that, for example, does not register withthe wireless network for a number of days, the message may never bedelivered, and instead discarded.

The SMPP gateway 104 forwards the response to the protocol gateway 102at 818. The protocol gateway 102 performs a conversion operation on theSMPP formatted response to create a SOAP formatted response. At 822, theSOAP formatted response is sent to the SMS application 201.

The billing server 702 can contain information regarding and/or haveaccess to information regarding wireless subscriber accounts. Accessingthis information can, for example, enable the billing server 702 toperform a check of the account status for the account associated with amobile terminal for which a wireless message is intended. If noinformation for the intended recipient can be located, the billingserver can, for example, notify the protocol gateway 102 so that nomessage delivery attempt is made. The account status check could alsoshow that the account is not in good standing. Message delivery may bedenied in this case as well. In addition, the subscriber associated withthe account may have indicated that she does not wish to be billed formessages so that no delivery attempt is made.

Where the account associated with the mobile terminal can not be billed,the SMS application 201 receives an error message from the protocolgateway 102. Accordingly, a SMS message is not delivered to the messagecenter or mobile terminal. A similar response can occur when the billingserver 702 is unavailable for purchase request, or when a message isreceived by the protocol gateway 102 is invalid.

FIG. 9 is a diagram 900 illustrating a bulk send of a message withbilling capability. At 902, the SMS Application 201 sends a bulk messagerequest in a SOAP format to the protocol gateway 102. This message islabeled “Submit_Bulk_SMS.REQ” on the diagram. At 904, the protocolgateway 102 sends a response to the bulk message request to the SMSapplication 201 confirming receipt of the bulk message request. Theprotocol gateway 102 can perform a conversion operation on the SOAPformatted message sent from the SMS application 201. The bulk messagerequest can contain the message to be sent which is common to allintended recipients along with information identifying the intendedrecipients. The protocol gateway 102 can create SMPP formatted messagesfrom the bulk message request for each of the intended recipients.

At 906, the protocol gateway 102 issues a purchase request to thebilling server 702. The purchase request can include information thatidentifies one of the wireless subscriber accounts where the bulkmessage is to be sent. At 908, the billing server 702 returns a responseto the purchase request to the protocol gateway 102. As mentioned abovewith respect to FIG. 8, the billing server 702 can perform a check todetermine if the intended recipient can be billed for the message. Ifnot, message delivery can be denied.

If the account associated with the intended recipient can be billed, at910 the protocol gateway 102 submits the SMPP formatted message for theintended recipient to SMPP gateway 104. At 912, the SMPP gateway 104sends a routing data request to the directory server 211. At step 914,the directory server returns a routing data response to the SMPP gateway104 indicating which message center the SMPP Gateway should send therequest to for delivery. At step 916, the SMPP gateway 104 submits thesend request to the message center 215 for delivery.

At 918, the message center 215 issues a response confirming that themessage has been received at the message center. This is not aconfirmation that the message has been delivered; only that it has beenreceived at the message center. The confirmation response is sent fromthe message center 215 to the SMPP Gateway 104. The SMPP gateway 104forwards this response to the protocol gateway 102 at 920. The protocolgateway 102 records that one of the bulk messages was received at themessage center 215. The destination address of the original message canbe used to identify to which of the intended recipients that theconfirmation message corresponds.

The actions at 906, 908, 910, 912, 914, 916, 918, and 920 enclosed indotted line 923 are repeated for each destination address in the bulksend request.

At 924, the protocol gateway 102 sends a SOAP formatted message to theSMS application to confirm that the plurality of messages correspondingto the initial bulk status request were received by their respectivemessage centers. This message may indicate which, if any, deliveryattempts were completed, and which resulted in failure. At 926, the SMSapplication 201 sends a response to the protocol gateway 102 to indicatethat the confirmation was received.

Thus, the protocol gateway 102 allows the SMS application 201 to submita single message and a list of destination addresses for delivery toeach address. A destination address can be, for example, a mobiletelephone number. The protocol gateway 102 submits a purchase request toa billing server 702 for each message recipient, and collects responsesfor each message from their respective message centers (whethersuccessful or unsuccessful) and assembles them into a response, whichcan then be forwarded to the SMS application 201.

The SMS application 201 of the protocol gateway network architecture 100and the protocol gateway network architecture 700 can communicate withthe protocol gateway 102 using a SOAP format which is transported by,for example, a Hypertext Transfer Protocol (HTTP). Data transportbetween the SMS application and the protocol gateway 102 can occur usinga secured authentication of the SMS application 201 and data encryption.The SOAP message being exchanged by the protocol gateway 102 and the SMSapplication can include a header, a body, and mime attachments.

The communications between an SMS application 201 and a protocol gateway102 can comprise a number of message types. These messages containheaders that indicate the message type along with other logicalparameters. Along with the headers, the messages include bodyinformation that contains the data elements relevant to each of themessage types.

A typical header can include, for example, elements corresponding to atransaction ID, message type, protocol version and service provider ID.The transaction ID can be a unique identifier used for a set of messagescorresponding to a request to send an SMS message and any relatedmessages such as confirmation messages.

The message type can indicate what type of message to which the bodyinformation corresponds. Examples can include, Submit_SMS.REQ (forsubmitting a new request from an SMS application to the protocol gatewayfor sending an SMS message), Submit_SMS.RES (for the protocol gatewaysending a response to a request from a SMS application), Deliver_SMS.REQ(for sending a message center receipt confirmation from the protocolgateway to an SMS application), Deliver_SMS.RES (for an SMS applicationto respond to the protocol gateway that a message center receiptconfirmation was received), Delivery_Report.REQ (for sending a deliveryreport from the protocol gateway to an SMS application)Delivery_Report.RES (for sending a response from an SMS application tothe protocol gateway to indicate that a delivery report was received),Submit_Bulk_SMS.REQ (for submitting a bulk send request from an SMSapplication to the protocol gateway), Submit_Bulk_SMS.RES (for theprotocol gateway to respond to the SMS application indicating that abulk send request was received), Submit_Bulk_SMS_Status.REQ (for theprotocol gateway to send to the SMS application to indicate that a bulkmessage send was completed), Submit_Bulk_SMS_Status.RES (for an SMSapplication to acknowledge receipt of a bulk send complete message),Number_Validity.REQ (for submitting a number validity check request froman SMS application to the protocol gateway), Number_Validity.RES (forthe protocol gateway to indicate that a number validity check requestwas received), Number_Validity_Status.REQ (for the protocol gateway toreturn the results of a number validity check to an SMS application, andNumber_Validity_Status.RES (for an SMS application to confirm receipt ofthe results of a number validity check).

Body information can be specific to each message type. For example, thebody elements of a Submit_SMS.REQ can include: source address,destination address, delivery report requested, mobile terminatedcharging, charging information, and reference to MIME attachments. Thesource address can be the IP address of the SMS application that isrequesting that a message be sent. This may or may not include the portnumber at which the SMS application can be reached. The destinationaddress can be the mobile telephone number of the device intended toreceive the message being submitted. Delivery report request can be alogical field (‘1’ or ‘0’ or text ‘yes’ or ‘no’) that indicates whetheror not the SMS application requests a delivery report for the message.Mobile terminated charging can be a logical field that indicates whetheror not the mobile recipient is to be charged for the message content.Charging information can include an identification of the product thatis being delivered (for example, the name of a purchased telephonebackground photo), quantity purchased, description, etc. Reference toMIME attachment can include information that points to content to beattached to a message to the mobile recipient.

Body fields for a Submit_SMS.RES message can include request status,error code, message ID, and charging results information, The requeststatus field can indicate the status of the message submissioncorresponding to this response. Error code can contain informationregarding any error codes that are associated with the message deliveryattempt. Message ID can include information that identifies the messageto which this response corresponds. Charging results information caninclude the status of the purchase, a status message, quantitypurchased, description, etc.

By providing a protocol gateway between a SMS application and a SMPPgateway, a simplified interface is provided for communicating messages.Thus, SMS applications are not required to maintain any knowledge of theSMPP protocol, which is a protocol that is less well known than SOAP,more difficult to work with, and can require specific knowledge of awireless network.

The law does not require and it is economically prohibitive toillustrate and teach every possible embodiment of the present claims.Hence, the above-described embodiments are merely exemplaryillustrations of implementations set forth for a clear understanding ofthe principles of the invention. Variations, modifications, andcombinations may be made to the above-described embodiments withoutdeparting from the scope of the claims. All such variations,modifications, and combinations are included herein by the scope of thisdisclosure and the following claims.

The invention claimed is:
 1. A method, associated with delivery of shortmessage service messages, comprising: receiving, by a gateway having aprocessor, delivery responses confirming that short message servicemessages have been sent to a plurality of destination addresses, each ofthe short message service messages having identical message content;assembling, by the gateway, the delivery responses to generate acomposite response; sending, by the gateway, the composite response to ashort message service application; receiving, by the gateway, from theshort message service application, a validity request being formatted ina first, simple-object-access, protocol and identifying multipleaddresses of the destination addresses; converting, by the gateway, thevalidity request, identifying the multiple addresses, from the first,simple-object-access, protocol into a plurality of queries, each of thequeries being formatted according to a second,lightweight-directory-access, protocol and including one of the multipleaddresses; sending, by the gateway, in a second sending act, one of thequeries, being formatted according to the second,lightweight-directory-access, protocol, to a service for verification ofthe address of the query; receiving, by the gateway, from the service,in a second receiving act, a validity response message responding to thequery sent and being formatted according to the second,lightweight-directory-access, protocol; repeating, in connection witheach remaining query of the plurality of queries, the second sending andthe second receiving acts; assembling the validity response messagesreceived to create a composite validity response message being formattedaccording to the first, simple-object-access, protocol; and sending, tothe short message service application, the composite validity responsemessage being formatted according to the first, simple-object-access,protocol.
 2. The method of claim 1, further comprising receiving, fromthe short message service application, a bulk short message servicerequest including the identical message content and the plurality ofdestination addresses and being formatted in the first protocol.
 3. Themethod of claim 2, further comprising obtaining a separate short messageservice send request in the second protocol for each of the destinationaddresses of the bulk short message service request, each send requestincluding the identical message content.
 4. The method of claim 3,wherein obtaining the separate send request for each of the destinationaddresses includes: converting the bulk short message service requestfrom the first protocol to the second protocol; and generating theseparate send request in the second protocol for each of the destinationaddresses of the bulk short message service request.
 5. The method ofclaim 3, wherein: the gateway is a first gateway; and the method furthercomprises sending the separate short message service send requests to asecond gateway for delivery to the destination addresses.
 6. The methodof claim 2, wherein the bulk short message service request includes adelivery notification flag.
 7. The method of claim 6, wherein: thegateway is a first gateway; and the method further comprises: obtaininga separate send request in the second protocol for each of thedestination addresses of the bulk short message service request, eachsend request including the identical message content and the deliverynotification flag; and sending the separate short message service sendrequests, including the identical message content and the notificationflag, to a second gateway for delivery to the destination addresses. 8.The method of claim 2, wherein: the short message service messages areassociated with the bulk short message service request, the shortmessage service messages having been sent to the plurality ofdestination addresses in response to receiving the bulk short messageservice request; and the method further comprises billing a subscribercorresponding to one of the destination addresses for receiving theshort message service message associated with the bulk short messageservice request.
 9. The method of claim 1, further comprising providing,to a billing server, a purchase request comprising at least one piece ofdata selected from a group of data consisting of: a type of the messagecontent; a price of the message content; a mobile telephone numbercorresponding to a mobile account to be billed by the billing server; anamount of data to be sent to a mobile device associated with the mobiletelephone number; and an amount to be charged to the mobile account. 10.The method of claim 1, wherein: the service is configured to receivemultiple destination addresses in a single validity request; and themethod further comprises: sending, to the service for verification, atleast one combined query having more than one of the distinctionaddresses; and receiving, by the gateway, from the service, a validityresponse message responding to the combined query sent.
 11. A systemcomprising: a processor; and a computer-readable medium being incommunication with the processor and having stored thereoncomputer-executable instructions that, when executed by the processor,cause the processor to perform operations, associated with delivery ofshort message service messages, comprising: receiving delivery responsesconfirming that short message service messages have been sent to aplurality of destination addresses, each of the short message servicemessages having identical message content; assembling the deliveryresponses to generate a composite response; sending the compositeresponse to a short message service application; receiving, from theshort message service application, a validity request being formatted ina first, simple-object-access, protocol and identifying multipleaddresses of the destination addresses; converting, the validityrequest, identifying the multiple addresses, from the first,simple-object-access, protocol into a plurality of queries, each of thequeries being formatted according to a second,lightweight-directory-access, protocol and including one of the multipleaddresses; sending, in a second sending act, one of the queries, beingformatted according to the second, lightweight-directory-access,protocol, to a service for verification of the address of the query;receiving, from the service, in a second receiving act, a validityresponse message responding to the query sent and being formattedaccording to the second, lightweight-directory-access, protocol; andrepeating, in connection with each remaining query of the plurality ofqueries, the second sending and the second receiving acts; assemblingthe validity response messages to create a composite validity responsemessage being formatted according to the first, simple-object-access,protocol; and sending, to the short message service application, thecomposite validity response being formatted according to the first,simple-object-access, protocol.
 12. The system of claim 11, wherein theoperations further comprise receiving, from the short message serviceapplication, a bulk short message service request including theidentical message content and the plurality of destination addresses andbeing formatted in the first protocol.
 13. The system of claim 12,wherein the operations further comprise: converting the bulk shortmessage service request from the first protocol to the second protocol;generating a separate short message service send request in the secondprotocol for each of the destination addresses of the bulk short messageservice request; and sending the separate short message service sendrequests, including the identical message content, to a gateway fordelivery to the destination addresses.
 14. The system of claim 12,wherein: the bulk short message service request includes a deliverynotification flag; the operations further comprise: obtaining a separateshort message service send request in the second protocol for each ofthe destination addresses of the bulk short message service request,each short message service send request including the identical messagecontent and the delivery notification flag; and sending the separateshort message service send requests, including the identical messagecontent and the notification flag, to a gateway for delivery to thedestination addresses; and receiving, in response to sending theseparate short message service send requests, including the identicalmessage content and the notification flag, a separate deliverynotification, in the second protocol, from the gateway, in connectionwith each of the destination addresses.
 15. The system of claim 11,wherein: the service is configured to receive multiple destinationaddresses in a single validity request; and the operations furthercomprise: sending, to the service for verification, at least onecombined query having more than one of the distinction addresses; andreceiving, from the service, a validity response message responding tothe combined query sent.
 16. A computer-readable storage device havingstored thereon computer-executable instructions that, when executed by aprocessor, cause the processor to perform operations, associated withdelivery of short message service messages, comprising: receivingdelivery responses confirming the sending of short message servicemessages to a plurality of destination addresses, each of the shortmessage service messages having identical message content; assemblingthe delivery responses to generate a composite response; sending thecomposite response to a short message service application; receiving,from the short message service application, a validity request beingformatted in a first, simple-object-access, protocol and identifyingmultiple addresses of the destination addresses; converting, thevalidity request, identifying the multiple addresses, from the first,simple-object-access, protocol into a plurality of queries, each of thequeries being formatted according to a second,lightweight-directory-access, protocol and including one of the multipleaddresses; sending, in a second sending act, one of the queries, beingformatted according to the second, lightweight-directory-access,protocol, to a service for verification of the address of the query;receiving, from the service, in a second receiving act, a validityresponse message responding to the query sent and being formattedaccording to the second, lightweight-directory-access, protocol;repeating, in connection with each remaining query of the plurality ofqueries, the second sending and the second receiving acts assembling thevalidity response messages to create a composite validity responsemessage and being formatted according to the first,simple-object-access, protocol; and sending, to the short messageservice application, the composite validity response message beingformatted according to the first, simple-object-access, protocol. 17.The computer-readable storage device of claim 16, wherein: the serviceis configured to receive multiple destination addresses in a singlevalidity request; and the operations further comprise: sending, to theservice for verification, at least one combined query having more thanone of the distinction addresses; and receiving, from the service, avalidity response message responding to the combined query sent.